Repository navigation
Task/FOUR-34405: Persist screen input data for preview and create data scenarios list - #9168
Conversation
Persist named preview data presets for screens and versions, expose them through the screen API and MCP tools, and add Screen Builder controls to create, edit, reorder, apply, and update presets.
PR SummaryMedium Risk Overview Screen Builder’s Data Input panel now exposes preset CRUD, selection, dirty-state update/discard, and drag-to-reorder, wiring Reviewed by Cursor Bugbot for commit 0890c34. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 0890c34. Configure here.
| }, | ||
| onPreviewPresetsReorder() { | ||
| this.persistPreviewPresets(); | ||
| }, |
There was a problem hiding this comment.
Reorder desyncs selected preset
Medium Severity
Dragging presets reorders previewPresets but leaves activePreviewPresetIndex pointing at the old slot. The radio stays on a different scenario, and Update writes the current JSON into the wrong preset. List items also use the array index as :key, so Vue can reuse the wrong row after a drag. Removing a preset has the same index problem for an open edit card via previewPresetEditIndex.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit 0890c34. Configure here.


Summary
Refine PM4 screen guidance to require branch-specific, visibly distinct Preview presets and verify Public Files URLs before using them. Document avoiding silent URL rewrites and large asset imports, with related verification and checklist updates.
Screen.Recording.2026-11-13.at.5.21.19.PM.mov
Related tickets and PRs
https://processmaker.atlassian.net/browse/FOUR-34405